Touch prediction for visual displays

ABSTRACT

Touch events can be predicted relative to a visual display by maintaining a database of aggregated touch event history data relative to the visual display and from a plurality of touch screen devices. The database can be queried according to a set of input parameters defining an environment for use of the visual display. The results from the querying of the database can be analyzed to predict a set of touch events within the environment and based upon inferences obtained from the results. A representation of the set of touch events can be displayed along with the visual display.

BACKGROUND

The present disclosure relates to analysis of touch events relating tovisual displays, and more specifically, to predicting touch events for avisual display.

Touch screens are used by a growing number of people and for an everincreasing set of applications. The amount of data generated from use oftouch screens is also increasing. A particular type of generated datarelates to touch events that may be associated with a visual display.This data has the potential to provide a variety of insights about theindividuals using the visual display as well as about the visual displayitself.

SUMMARY

Various embodiments are directed toward a method for predicting touchevents relating to a visual display. The method can include maintaininga database of aggregated touch event history data relative to the visualdisplay and from a plurality of touch screen devices; querying thedatabase according to a set of input parameters defining an environmentfor use of the visual display; analyzing results from the querying ofthe database to predict a set of touch events within the environment andbased upon inferences obtained from the results; and displaying arepresentation of the set of touch events with the visual display.

Certain embodiments relate to a method for tracking touch eventsrelating to a visual display. The method can include accessing aplurality of touch event data sets for the visual display, each data setassociated with a corresponding electronic device; identifying touchpatterns from the touch event data sets; monitoring subsequent touchevents by users of the visual display; detecting a match between thetouch patterns and subsequent touch events of a particular user of theusers; predicting, in response to detecting the match, a possible touchevent for the particular user; and modifying, in response to thepossible touch event, the visual display for the particular user.

Consistent with embodiments a system can include one or more computerprocessor circuits and a computer readable storage medium that can haveprogram instructions embodied therewith. The program instructions canexecutable by the one or more computer processor circuits to cause thesystem to: maintain a database of aggregated touch event history datarelative to the visual display and from a plurality of touch screendevices; query the database according to a set of input parametersdefining an environment for use of the visual display; analyze resultsfrom the querying of the database to predict a set of touch eventswithin the environment and based upon inferences obtained from theresults; and display a representation of the set of touch events withthe visual display.

According to embodiments, a computer readable storage medium can haveprogram instructions embodied therewith. The program instructions canexecutable by the one or more computer processor circuits to cause thesystem to: maintain a database of aggregated touch event history datarelative to the visual display and from a plurality of touch screendevices; query the database according to a set of input parametersdefining an environment for use of the visual display; analyze resultsfrom the querying of the database to predict a set of touch eventswithin the environment and based upon inferences obtained from theresults; and display a representation of the set of touch events withthe visual display.

The above summary is not intended to describe each illustratedembodiment or every implementation of the present disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawings included in the present application are incorporated into,and form part of, the specification. They illustrate embodiments of thepresent disclosure and, along with the description, serve to explain theprinciples of the disclosure. The drawings are only illustrative ofcertain embodiments and do not limit the disclosure.

FIG. 1 depicts a block diagram of a system for monitoring and usingtouch event data for visual displays, consistent with embodiments of thepresent disclosure;

FIG. 2 depicts a flow diagram of a system for monitoring and using touchevent data associated with a visual display, consistent with embodimentsof the present disclosure;

FIG. 3 depicts a set of different example touch events for differentdevices and a resulting database table, consistent with embodiments ofthe present disclosure;

FIG. 4 depicts an interface that can be viewed by a reviewer oradministrator, consistent with embodiments of the present disclosure;

FIG. 5 depicts a process flow for using touch event history data togenerate predictive touch event sets, consistent with embodiments of thepresent disclosure;

FIG. 6 depicts a flow diagram for a system that can dynamically modify avisual display, consistent with embodiments of the present disclosure;

FIG. 7 depicts a cloud computing node, according to an embodiments ofthe present disclosure;

FIG. 8 depicts a cloud computing environment, according to embodimentsof the present disclosure; and

FIG. 9 depicts abstraction model layers, according to embodiments of thepresent disclosure.

While the invention is amenable to various modifications and alternativeforms, specifics thereof have been shown by way of example in thedrawings and will be described in detail. It should be understood,however, that the intention is not to limit the invention to theparticular embodiments described. On the contrary, the intention is tocover all modifications, equivalents, and alternatives falling withinthe spirit and scope of the invention.

DETAILED DESCRIPTION

Aspects of the present disclosure relate to analysis of touch eventsrelating to visual displays, more particular aspects relate topredicting touch events based upon touch event histories. While thepresent disclosure is not necessarily limited to such applications,various aspects of the disclosure may be appreciated through adiscussion of various examples using this context.

Various embodiments of the present disclosure are directed toward asystem that is configured to monitor touch events relating to a visualdisplay that can be shared with many different individuals using touchscreen capable devices. The system can be configured to operate as acloud based service that collects touch event information from the manydifferent individuals. A database of touch information can be createdand then used for a variety of different purposes. For instance, a userof the system can generate a query that specifies a particularenvironment for using a visual display. Touch event information that hasbeen collected can be used by the system to generate a set of predictedtouches for the environment and visual display. The prediction(s) can bepresented to the user in a response to the query.

According to embodiments, the viewing experience of one or moreindividuals can be recreated for a reviewing party. For instance,reviewers can be allowed to see where and how touches occurred withregards to a visual display (e.g., an image or interface). This caninclude the recreation of viewing experiences based upon sequence ofevents for a common set of touch sequences. Accordingly, a reviewer cansee the recreated view from the vantage point of the individuals thatoriginally used the visual display (e.g., a virtual recreation of howthe visual display was used showing each touch and the effect of thetouch, whether scrolling, zooming or other action). Consistent withcertain embodiments, this recreation can be based upon predicted touchevents relating to a query and associated environment.

Certain embodiments are directed toward a system that can determine aset of predicted touches for individuals actively using a visualdisplay. The set of predicted touches can then be used to modify theinteractive experience of the individuals in real time. For instance,the system can be configured to proactively highlight, enlarge, orotherwise modify a portion of the visual display that a particularindividual is predicted to touch in the future. Other actions arepossible, some of which are discussed in more detail herein.

Particular embodiments allow for a variety of different types ofadditional information to be linked to the touch events being recorded.For example, the additional information may specify dates and times,demographic data of the individual creating the touches, the types oftouches (e.g., single touch, double touch, scroll, pinch, multi-touchand others), the capabilities of the touchscreen capable device (e.g.,operations system, screen size, or touch screen capabilities). The datacan be accumulated using a cloud sourced solution that has thecapability to draw touch-based data from a large group of people andover a large period of time. Accordingly, the additional information canbe voluminous and varied. Aspects of the present disclosure allow forthe data to be accessed using a set of layers or filters that can beapplied when using the data for different purposes. For example, if theimage associated with the touches is related to the medical field (e.g.,a magnetic resonance image (MRI) of an individual), then it may behelpful to filter touches based upon whether the user is a medicalprofessional and further based upon their particular experience leveland specialty.

Embodiments of the present disclosure are directed toward generating aprediction of what touch events are likely to occur within a particularset of environment parameters. This can include identifying patterns andcorrelations between data collected for prior touch events and theparticular set of environment parameters. For instance, a machinelearning algorithm can be trained using the information collected forprior touch events. The machine learning algorithm can then be used topredict touch events for different sets of environment parameters. Forexample, the machine learning algorithm can use a supervised learningapproach in which the collected data is used to supervise, or train, thealgorithm. In certain embodiments, data filtering based upon desiredoutcomes can be used to further refine the prediction of touch events.

Certain embodiments are directed toward the use of predicted touches todynamically modify a visual display being actively used by anindividual. For instance, environment parameters for a person using avisual display can be collected while they are using the visual display.These parameters can be provided to a prediction engine that analyzesthe environment parameters and generates a prediction for future touchesof the user using data collected from past users of the same, orsimilar, user visual display. The predicted touches can then be used todynamically modify the visual display.

In an example of a dynamic modification, the visual display could bemodified to increase the size of the predicted touch area so that it ismore easily selected and viewed. Other modifications are also possible,such as increasing highlighting or emphasizing a portion of the visualdisplay. Another possible modification could be responsive to thepredicted touch event indicating that the viewing individual is likelyto want to view an item that is not currently visible (e.g., that wouldrequire scrolling or zooming out). The system can be configured toproactively move the item into current field of view, and thereby,facilitate the use of the visual display. It may also be possible toprefetch data corresponding to predicted touches (e.g., as may berelevant to an interactive interface such as a webpage).

Consistent with embodiments, a visual display modification can includesuggested alternatives related to the predicted touch. This may beuseful for steering the individual toward a desired use of the visualdisplay, or at least away from an undesired use. The suggestedalternatives can also include advertisements that are correlated to thepredicted touch events (e.g., if the touch event suggests interest in aparticular item shown by the visual display, relevant advertisements canbe displayed).

Various aspects of the present disclosure are directed towardfacilitating analysis and review of visual displays and their usage. Forinstance, a visual display containing one or more medical images (e.g.,X-ray or MRI) and diagnostic graphs or charts (e.g., electrocardiography(ECG)) can be shared with a community of doctors or other individuals,and touch event data can be collected. A reviewing individual (e.g., aprofessional treating a patient corresponding to the images or charts)can use the recorded touch data to identify points of interest indicatedby the community, glean information about the analysis process ofothers, and for other purposes. The system can also be configured toallow the reviewing individual to setup and apply various filters on thedata. In the medical example, the reviewing individual could filterbased upon doctor experience or specialty. The results of differentfilter could also be compared to assess the differences.

In various embodiments, a predictive touch engine can be used infacilitating analysis and review of visual displays and their usage. Forexample, a reviewing individual can submit a query to the system inorder to predict what touch events would occur in certain situations,which can be defined in terms of environment parameters. As an example,the reviewing individual may desire predictive information regarding awebsite and a particular demographic of users. The predictive engine canmake inferences to determine a set of likely touches for the demographicbased upon touch data collected from past users of the website. In thismanner, the reviewer can obtain useful information about likely use ofthe website even for a set of demographics for which there is little orno touch data.

Consistent with various aspects of the present disclosure, the systemcan allow for sharing of information in combination with the recordedtouch events. For example, individuals using the visual display canchoose to add annotations (e.g., text, audio or video) to touch events.In the medical environment, for instance, doctors could touch a point ofinterest on an image or chart and add in notes regarding thesignificance. The consolidated set of touch events and annotations canthen be reviewed and assessed by the source of the images or charts.

Turning now to the figures, FIG. 1 depicts a block diagram of a systemfor monitoring and using touch event data for visual displays,consistent with embodiments of the present disclosure. The system ofFIG. 1 can be configured to monitor touch events originating from userdevices 102, which can each have touch screen capabilities. The userdevices can include, but are not necessarily limited to, personalcomputers 104, smart phones 106 and tablet devices 108. For example, theuser devices 102 can obtain the visual display over a network 116 andthen display the visual display using a touch screen. A local module canbe initiated on the user device in order to monitor and record touchevent data that corresponds to the use of the visual display. Inparticular embodiments, the local module can be configured to storetouch event information substantially independent from active components(if any) of the visual display. For example, the visual display could bea photograph or other image without any intrinsic active selectioncomponents (e.g., as opposed to an active website with selectablebuttons, links or other interactive components).

According to certain embodiments, the local module can be configured totransmit the touch event data to a touch event monitoring module 112.The touch event monitoring module 112, and other modules and enginesdiscussed herein, can be stored on a computer readable medium asinstructions that are configured to run on one or more processorcircuits corresponding to one or more monitoring server devices 110. Thetouch event data can then be stored in a database 114, which canaggregate information from a large number of potential users over aperiod of time. The resulting touch event history can also includeadditional information relating to the environment of the touch events(e.g., user demographics, time, or geographic location).

A reviewer, or administrator, of the visual display can access thesystem using a computer device 130. The system can include a serverdevice 118 that provides a profile and access control module 120. Theaccess control module 120 can be configured to control access to thetouch event history data and to allow for customizations for differentreviewers based upon information stored in a profile database 122. Theprofile and access control module 120 can also handle security andverification of a reviewer or administrator (e.g., using user login andpassword checks or other verifications methods). For instance, eachreviewer can be authorized to access data for a set of one more displaysthat they can provide and control. The profile and access control module120 can verify the identity of an individual using a computer device 130and then allow access to portions of the touch event history database114 that correspond to the set of displays for the identifiedindividual. Other information can be stored such as user preferencesregarding previously used filters and environmental parameters.

In addition to accessing the data stored in the touch event historydatabase 114, the computing device 130 can generate queries forpredictive touch information. These queries can be sent to a serverdevice 124 that can be configured to include a predictive touch engine126. The predictive touch engine can be configured to respond to a queryby analyzing data stored in touch event history database 114 accordingto the query parameters and appropriate predictive parameters 128. Incertain embodiments, predictive touch engine 126 can train a machinelearning algorithm from data in the touch event history database 114.The training can be visual display specific and it can also includetraining across multiple visual displays. The results of the trainingcan be stored in the predictive parameters database 128. When a queryrequest for predictive touches for a visual display with certainenvironmental parameters is received, the predictive touch engine canapply the learning algorithm using the appropriate predictiveparameters. The resulting set of predictive touches can then be providedto satisfy the query.

Various embodiments allow for queries to be generated automatically andfor the predictive touch events for the query to be used in dynamic andreal time applications. For example, a visual display could be part of awebsite for which touch event data has been collected over a period oftime and for which the predictive touch engine is configured to generatepredictive touch event data. When a new user accesses the website, thetouch event monitoring module 112 can send queries to the predictivetouch engine using environmental parameters matching the browsingsession of the new user. The predictive touches returned as part of thequeries can then be used to modify the viewing experience of the newuser. This can include, but is not limited to, highlighting portions ofthe visual display that are likely to be touched, changing the size ofportions of the visual display, automatically scrolling a portion of thedisplay, customizing advertisements and prefetching data expected to beneeded due to a predicted set of touches.

FIG. 2 depicts a flow diagram of a system for monitoring and using touchevent data associated with a visual display, consistent with embodimentsof the present disclosure. Touch screen devices 202, 206 can beconfigured to include a touch record module 204, 208. The touch recordmodule 204, 208 can monitor touch events associated with one or morevisual displays. The visual displays can be provided by a displayprovider 210. Display provider 210 can include one or more computers orservers that are accessible over a network, such as the global Internet.Consistent with certain embodiments, display provider 210 can alsoprovide a touch record module 212 for download by touch screen devices.The display provider 210 can also use a version of a touch record module212 that collects touch event data from touch screen devices 202, 206.

For instance, a touch record module 204, 208 can be installed by a userof a touch screen device, whether from display provider 210 or fromother sources. The user can expressly initiate the touch record module204, 208 when using a visual display for which touch event data isrelevant, or the module can be automatically initiated upon detectingthat a valid visual display is accessed. In certain embodiments, themodule can be downloaded and initiated in response to accessing aremotely provided visual display. For example, the module can be run asan embedded application operating within a web browser application.

Consistent with various embodiments, the touch record modules 204, 208can be configured to allow a user to enable or disable the recordingfeature depending upon their preference. The modules can also beconfigured to allow a user to add additional information with touchevents, such as adding text or audio to a touch point. As an example, adoctor could touch a portion of a visual display and select anannotation option provided by touch record module 204, 208. Theadditional annotation material added by the doctor can then be providedfor storage in a touch information repository or database 214, alongwith the touch event indications.

According to embodiments, an administrative interface 218 can beprovided to reviewers and administrators of the visual displays. Theinterface can be designed to allow the reviewers to generate queriesregarding visual displays and touch event history data. For example, areviewer may seek information regarding a particular set ofenvironmental parameters. As an example, a reviewer of a visual displaythat is part of a website might create a query with the environmentalparameters that include demographic information for users and touchscreen capabilities (e.g., screen resolution). The parameters might beselected in order to understand usage patterns and identify potentialproblems with the website use and flow.

Queries from the administrative interface 218 can be provided to a datafilter and touch type parser module 216 (hereafter referred to as a“data filter module”). The data filter module 216 can filter data basedupon the query parameters. This can include filtering touch eventhistory data based upon the particular visual display(s) for the queryand based on various environmental parameters. For example, a reviewerseeking medical-based data could generate a query that filters databased upon experience and specialty of the source of the touch events.The data filter module 216 can also be configured to parse touch eventdata according to the type of touch. This can include identifying touchevents such as zoom (in or out), scroll, double touches and others.Touches can then be parsed and associated according to these identifiedtouch event types. In certain embodiments, this type of parsing can bedone before data is stored in the touch information repository ordatabase 214.

In various embodiments, the touch data history can be used by apredictive algorithm trainer 220 to train parameters used by apredictive algorithm 220 based upon data from the touch info repository214. In certain embodiments, the training can be carried out usingfiltered and parsed data 216. Various embodiments also contemplatetraining being carried out using unfiltered data, which might also becarried out before queries are received.

The trained parameters can be used by predictive algorithm 222 togenerate a set of predictive touches for the query and associatedenvironmental parameters. The predicted touches can then be providedalong with the visual display from the display provider 210 to satisfythe query from administrative interface 218. In certain embodiments, thepredicted touch events can be provided to a display recreation module224. Display recreation module can be configured to generate areplication of what a user would see relative to the touch environmentin the query and in response to the predicted touch events. For example,the predicted touch events may include a sequence of zooming andrepositioning touches that can be recreated so that the reviewer can seewhat a user would be viewing while the touch events are carried out.

Consistent with various embodiments, the system can be designed to allowa reviewer to also review touch event history directly (e.g., with orwithout the use of predictive touch events). This ability can be used inconnection with express annotations and input from the generators of thetouch event history. Particular embodiments allow a review to identify asource of particular touch events or annotations and elicit furtherinformation from the identified source. For example, a reviewing doctormay seek further details regarding their technique for analyzing adisplay or their reason for focusing on a particular item.

Various embodiments also allow for users of the visual display to viewcomments and touch events of other users. For example, participantvoting and additional comments can be used to further refine sharedexperience (e.g., doctors may disagree with one comment and vote downand/or add contrary input). The results of this collaborative effort canbe provided to the reviewers and to the participants.

As discussed herein, embodiments of the present disclosure allow forqueries to be generated dynamically and for the resulting predictivetouches to be used to modify the visual display in real time. Forexample, the visual display provider server 210 can be configured togenerate dynamic queries for users actively using a visual display, suchas a website. The results of the query can be provided back to thevisual display provider server 210 and used to improve the viewingexperience of the users by dynamically modifying the visual displayduring its use.

FIG. 3 depicts a set of different example touch events for differentdevices and a resulting database table, consistent with embodiments ofthe present disclosure. Displays 302, 308 and 316 depict differentexample screen sizes and orientations that might be used to show avisual display containing an element 304. The visual display is shown asincluding element 304 that is a simple diamond for illustrativepurposes. The visual display, however, can include a variety of complexand different elements, including but not necessarily limited to, text,selectable icons, dropdown menus, images, embedded videos, and animatedimages.

Display 302 shows rectangular display screen with a horizontal(portrait) orientation and as single touch event 306. Display 308 showsa wider display screen having two touch points 312 and 314 that alsoinclude motion indicated by the arrows. This type of touch event mayindicate that the user zoomed out to view more of the visual display.Display 316 shows another rectangular display screen that is in avertical (landscape) orientation. A touch even 320 is indicated with adownward motion component shown by an arrow. This type of motion mayindicate repositioning or scrolling was done by the user.

Consistent with embodiments of the present disclosure, the touch eventsfor the different devices can be stored in a database or repository 322.Non-limiting examples of data that can be stored in the repositoryinclude touch location (e.g., XY coordinates referenced to the visualdisplay), touch duration, touch motion, touch type (if parsing is doneprior to queries), and touch context (including data implicitly orexplicitly provided by a user).

FIG. 4 depicts an interface that can be viewed by a reviewer oradministrator, consistent with embodiments of the present disclosure.Interface 402 can be provided using an administrative interface (e.g.,as discussed in connection with FIG. 2). Display portion 410 canrecreate the visual display, having one or more display elements 412,within the environment associated with the query. For example, theenvironment may specify a touch screen size and resolution. Thepredicted touch events 414, 416 can be shown on the display portion.Additional information for the predicted touch events can also bedisplayed. This may include motion associated with the touch events, asindicated by the arrows (other ways of showing motion are possible), andcontext and annotations 418. The context and annotations 418 can changedepending upon which touch events are selected by the reviewer.

In certain embodiments, the predictive engine can generate multiple setsof predicted touch events that each have a different predictivelikelihood of occurring. These different sets are displayed inselectable boxes 404, 406, 408 that can include a probability percentageindicating how likely each set is to occur. For example, a touch set A(404) can be determined to be 70% likely to occur, a touch set B (406)can be determined to be 20% likely, and a touch set C (408) can bedetermined to be 10% likely. The interface 402 can present thisinformation in a variety of manners, which can be selected by thereviewer. For instance, the different touch event sets can be displayedwhen selected by the reviewer. This may allow for individual review ofeach or for multiple touch sets to be displayed simultaneously.

FIG. 5 depicts a process flow for using touch event history data togenerate predictive touch event sets, consistent with embodiments of thepresent disclosure. A touch monitoring system can be configured togenerate and maintain a database of aggregated touch event history datarelative to the visual display and from a plurality of touch screendevices, as shown by block 502. This can include the use of varioustouch monitoring modules and collecting and aggregating data from alarge number of potential user devices using a shared pool ofconfigurable computing resources.

The maintained database can then be queried according to a set of inputparameters defining an environment for use of the visual display, perblock 504. This may include an environment that is defined in terms ofparameters such as time of year or day, viewing device capabilities,user demographics, geographic location of viewing device, and connectionbandwidth.

The results of the query of the database can then be received, per block506, and then analyzed and used to predict a set of touch events withinthe environment and based upon inferences obtained from the results, perblock 508. For example, the environment may specify a set of parametersfor which there is little or no direct touch event history. Accordingly,a predictive algorithm can be used to infer likely touch events fromtouch event history from similar environments.

Consistent with embodiments, the predictive touch events can be providedto the query source (e.g., reviewer) using a representation of the setof touch events with the visual display, per block 510. This may includedisplaying the visual display with shading or other indications of wherethe predicted touch events are located on the display.

Embodiments allow for multiple different queries to be generated andserviced, accordingly the system can determine whether or not there areadditional or new queries, per block 512. If there are new queries, thesystem can query the database, per block 504, and then repeat theprocess flow described above. If there are not any new queries, then thesystem can continue to monitor touch events, per block 518 and maintainthe database per block 502.

In certain embodiments, the system can be configured to determinewhether or not to use information from the predictive touch events toupdate or modify the visual display, per block 514. This can includemodifications that are automatically carried out (such as real timemodifications made while a user is accessing a website with the visualdisplay) or in response to input from a reviewer. If it is determinedthat the display is to be updated, then the system can carry out thechangers per block 516.

FIG. 6 depicts a flow diagram for a system that can dynamically modify avisual display, consistent with embodiments of the present disclosure.The system can monitor the display usage, per block 602. For example,the user selections and touch events can be monitored and recorded asthe user is accessing the visual display, such as a website. The systemcan then analyze the monitored data and learned touch parameters togenerate a set of predicted touches for the user, per block 604. Asdiscussed herein, the parameters can be developed from training of amachine learning algorithm from past touch event data that has beencollected and analyzed.

The system can then determine whether or not the predicted touchessignify that a modification to the visual display is warranted, perblock 606. For example, the predicted touches may indicate that the useris likely to zoom into a particular portion of the visual display. Thissort of action can be flagged to indicate a modification is necessary(e.g., in order to proactively enlarge the particular portion). Othertriggering predicted touches are also possible. If no modification isindicated, the system can continue to monitor the visual display usage,per block 602. If a modification is indicated, the system can generate aset of display modification instructions, per block 608. The visualdisplay can then be updated, as shown by block 610.

It is understood in advance that although this disclosure includes adetailed description on cloud computing, implementation of the teachingsrecited herein are not limited to a cloud computing environment. Rather,embodiments of the present invention are capable of being implemented inconjunction with any other type of computing environment now known orlater developed.

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g. networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of the service. This cloud model may includeat least five characteristics, at least three service models, and atleast four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provisioncomputing capabilities, such as server time and network storage, asneeded automatically without requiring human interaction with theservice's provider.

Broad network access: capabilities are available over a network andaccessed through standard mechanisms that promote use by heterogeneousthin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to servemultiple consumers using a multi-tenant model, with different physicaland virtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but may be able to specify location at a higher levelof abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elasticallyprovisioned, in some cases automatically, to quickly scale out andrapidly released to quickly scale in. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.

Measured service: cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (e.g., storage,processing, bandwidth, and active user accounts). Resource usage can bemonitored, controlled, and reported providing transparency for both theprovider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer isto use the provider's applications running on a cloud infrastructure.The applications are accessible from various client devices through athin client interface such as a web browser (e.g., web-based e-mail).The consumer does not manage or control the underlying cloudinfrastructure including network, servers, operating systems, storage,or even individual application capabilities, with the possible exceptionof limited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer isto deploy onto the cloud infrastructure consumer-created or acquiredapplications created using programming languages and tools supported bythe provider. The consumer does not manage or control the underlyingcloud infrastructure including networks, servers, operating systems, orstorage, but has control over the deployed applications and possiblyapplication hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to theconsumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for anorganization. It may be managed by the organization or a third party andmay exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by severalorganizations and supports a specific community that has shared concerns(e.g., mission, security requirements, policy, and complianceconsiderations). It may be managed by the organizations or a third partyand may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the generalpublic or a large industry group and is owned by an organization sellingcloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or moreclouds (private, community, or public) that remain unique entities butare bound together by standardized or proprietary technology thatenables data and application portability (e.g., cloud bursting forload-balancing between clouds).

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure comprising anetwork of interconnected nodes.

Referring now to FIG. 7, a schematic of an example of a cloud computingnode is shown. Cloud computing node 10 is only one example of a suitablecloud computing node and is not intended to suggest any limitation as tothe scope of use or functionality of embodiments of the inventiondescribed herein. Regardless, cloud computing node 10 is capable ofbeing implemented and/or performing any of the functionality set forthhereinabove.

In cloud computing node 10 there is a computer system/server 12, whichis operational with numerous other general purpose or special purposecomputing system environments or configurations. Examples of well-knowncomputing systems, environments, and/or configurations that may besuitable for use with computer system/server 12 include, but are notlimited to, personal computer systems, server computer systems, thinclients, thick clients, hand-held or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputer systems, mainframecomputer systems, and distributed cloud computing environments thatinclude any of the above systems or devices, and the like.

Computer system/server 12 may be described in the general context ofcomputer system-executable instructions, such as program modules, beingexecuted by a computer system. Generally, program modules may includeroutines, programs, objects, components, logic, data structures, and soon that perform particular tasks or implement particular abstract datatypes. Computer system/server 12 may be practiced in distributed cloudcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed cloud computing environment, program modules may be locatedin both local and remote computer system storage media including memorystorage devices.

As shown in FIG. 7, computer system/server 12 in cloud computing node 10is shown in the form of a general-purpose computing device. Thecomponents of computer system/server 12 may include, but are not limitedto, one or more processors or processing units 16, a system memory 28,and a bus 18 that couples various system components including systemmemory 28 to processor 16.

Bus 18 represents one or more of any of several types of bus structures,including a memory bus or memory controller, a peripheral bus, anaccelerated graphics port, and a processor or local bus using any of avariety of bus architectures. By way of example, and not limitation,such architectures include Industry Standard Architecture (ISA) bus,Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, VideoElectronics Standards Association (VESA) local bus, and PeripheralComponent Interconnect (PCI) bus.

Computer system/server 12 typically includes a variety of computersystem readable media. Such media may be any available media that isaccessible by computer system/server 12, and it includes both volatileand non-volatile media, removable and non-removable media.

System memory 28 can include computer system readable media in the formof volatile memory, such as random access memory (RAM) 30 and/or cachememory 32. Computer system/server 12 may further include otherremovable/non-removable, volatile/non-volatile computer system storagemedia. By way of example only, storage system 34 can be provided forreading from and writing to a non-removable, non-volatile magnetic media(not shown and typically called a “hard drive”). Although not shown, amagnetic disk drive for reading from and writing to a removable,non-volatile magnetic disk (e.g., a “floppy disk”), and an optical diskdrive for reading from or writing to a removable, non-volatile opticaldisk such as a CD-ROM, DVD-ROM or other optical media can be provided.In such instances, each can be connected to bus 18 by one or more datamedia interfaces. As will be further depicted and described below,memory 28 may include at least one program product having a set (e.g.,at least one) of program modules that are configured to carry out thefunctions of embodiments of the invention.

Program/utility 40, having a set (at least one) of program modules 42,may be stored in memory 28 by way of example, and not limitation, aswell as an operating system, one or more application programs, otherprogram modules, and program data. Each of the operating system, one ormore application programs, other program modules, and program data orsome combination thereof, may include an implementation of a networkingenvironment. Program modules 42 generally carry out the functions and/ormethodologies of embodiments of the invention as described herein.

Computer system/server 12 may also communicate with one or more externaldevices 14 such as a keyboard, a pointing device, a display 24, etc.;one or more devices that enable a user to interact with computersystem/server 12; and/or any devices (e.g., network card, modem, etc.)that enable computer system/server 12 to communicate with one or moreother computing devices. Such communication can occur via Input/Output(I/O) interfaces 22. Still yet, computer system/server 12 cancommunicate with one or more networks such as a local area network(LAN), a general wide area network (WAN), and/or a public network (e.g.,the Internet) via network adapter 20. As depicted, network adapter 20communicates with the other components of computer system/server 12 viabus 18. It should be understood that although not shown, other hardwareand/or software components could be used in conjunction with computersystem/server 12. Examples, include, but are not limited to: microcode,device drivers, redundant processing units, external disk drive arrays,RAID systems, tape drives, and data archival storage systems, etc.

Referring now to FIG. 8, illustrative cloud computing environment 50 isdepicted. As shown, cloud computing environment 50 comprises one or morecloud computing nodes 10 with which local computing devices used bycloud consumers, such as, for example, personal digital assistant (PDA)or cellular telephone 54A, desktop computer 54B, laptop computer 54C,and/or automobile computer system 54N may communicate. Nodes 10 maycommunicate with one another. They may be grouped (not shown) physicallyor virtually, in one or more networks, such as Private, Community,Public, or Hybrid clouds as described hereinabove, or a combinationthereof. This allows cloud computing environment 50 to offerinfrastructure, platforms and/or software as services for which a cloudconsumer does not need to maintain resources on a local computingdevice. It is understood that the types of computing devices 54A-N shownin FIG. 8 are intended to be illustrative only and that computing nodes10 and cloud computing environment 50 can communicate with any type ofcomputerized device over any type of network and/or network addressableconnection (e.g., using a web browser).

Referring now to FIG. 9, a set of functional abstraction layers providedby cloud computing environment 50 (FIG. 8) is shown. It should beunderstood in advance that the components, layers, and functions shownin FIG. 9 are intended to be illustrative only and embodiments of theinvention are not limited thereto. As depicted, the following layers andcorresponding functions are provided:

Hardware and software layer 60 includes hardware and softwarecomponents. Examples of hardware components include mainframes, in oneexample IBM® zSeries® systems; RISC (Reduced Instruction Set Computer)architecture based servers, in one example IBM pSeries® systems; IBMxSeries® systems; IBM BladeCenter® systems; storage devices; networksand networking components. Examples of software components includenetwork application server software, in one example IBM WebSphere®application server software; and database software, in one example IBMDB2® database software. (IBM, zSeries, pSeries, xSeries, BladeCenter,WebSphere, and DB2 are trademarks of International Business MachinesCorporation registered in many jurisdictions worldwide).

Virtualization layer 62 provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers;virtual storage; virtual networks, including virtual private networks;virtual applications and operating systems; and virtual clients.

In one example, management layer 64 may provide the functions describedbelow. Resource provisioning provides dynamic procurement of computingresources and other resources that are utilized to perform tasks withinthe cloud computing environment. Metering and Pricing provide costtracking as resources are utilized within the cloud computingenvironment, and billing or invoicing for consumption of theseresources. In one example, these resources may comprise applicationsoftware licenses. Security provides identity verification for cloudconsumers and tasks, as well as protection for data and other resources.User portal provides access to the cloud computing environment forconsumers and system administrators. Service level management providescloud computing resource allocation and management such that requiredservice levels are met. Service Level Agreement (SLA) planning andfulfillment provide pre-arrangement for, and procurement of, cloudcomputing resources for which a future requirement is anticipated inaccordance with an SLA.

Workloads layer 66 provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation; software development and lifecycle management; virtualclassroom education delivery; data analytics processing; and transactionprocessing; and mobile desktop.

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Smalltalk, C++ or the like, andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

The descriptions of the various embodiments of the present disclosurehave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the describedembodiments. The terminology used herein was chosen to explain theprinciples of the embodiments, the practical application or technicalimprovement over technologies found in the marketplace, or to enableothers of ordinary skill in the art to understand the embodimentsdisclosed herein.

What is claimed is:
 1. A method for tracking touch events relating to avisual display on a first electronic device, the method comprising:identifying a set of environmental parameters, wherein the environmentalparameters provide information regarding an environment in which thevisual display is used on the first electronic device by a user;accessing a plurality of touch event data sets for the visual display,the plurality of touch event data sets corresponding to theenvironmental parameters and associated with the visual display as usedon at least a second electronic device; identifying touch patterns fromthe plurality of touch event data sets; monitoring subsequent touchevents by the user of the visual display; detecting a match between thetouch patterns and the subsequent touch events of the user; predicting,in response to detecting the match, a possible touch event for the user;and modifying, in response to the possible touch event, the visualdisplay on the first electronic device for the user.
 2. The method ofclaim 1, wherein the touch event data sets specify sequences of touchevents, touch coordinates relative to the visual display and differenttypes of touch events.
 3. The method of claim 1, wherein modifying thevisual display includes moving an item into a field of view of thevisual display.
 4. The method of claim 1, wherein modifying the visualdisplay includes displaying touch event data of other users.
 5. Themethod of claim 1, wherein the touch patterns comprise at least onetouch event performed on a visual display that lacks an interactivecomponent.
 6. A system comprising: a processor; and a memory incommunication with the processor, the memory containing programinstructions that, when executed by the processor, are configured tocause the processor to perform a method for tracking touch eventsrelating to a visual display on a first electronic device, the methodcomprising: identifying a set of environmental parameters, wherein theenvironmental parameters provide information regarding an environment inwhich the visual display is used on the first electronic device by auser; accessing a plurality of touch event data sets for the visualdisplay, the plurality of touch event data sets corresponding to theenvironmental parameters and associated with the visual display as usedon at least a second electronic device; identifying touch patterns fromthe plurality of touch event data sets; monitoring subsequent touchevents by the user of the visual display; detecting a match between thetouch patterns and the subsequent touch events of the user; predicting,in response to detecting the match, a possible touch event for the user;and modifying, in response to the possible touch event, the visualdisplay on the first electronic device for the user.
 7. The system ofclaim 6, wherein the touch event data sets specify sequences of touchevents, touch coordinates relative to the visual display and differenttypes of touch events.
 8. The system of claim 6, wherein modifying thevisual display includes moving an item into a field of view of thevisual display.
 9. The system of claim 6, wherein modifying the visualdisplay includes displaying touch event data of other users.
 10. Thesystem of claim 6, wherein the touch patterns comprise at least onetouch event performed on a visual display that lacks an interactivecomponent.
 11. A computer program product, the computer program productcomprising a computer readable storage medium having programinstructions embodied therewith, the program instructions executable bya computer to cause the computer to track touch events relating to avisual display on a first electronic device, the tracking comprising:identifying a set of environmental parameters, wherein the environmentalparameters provide information regarding an environment in which thevisual display is used on the first electronic device by a user;accessing a plurality of touch event data sets for the visual display,the plurality of touch event data sets corresponding to theenvironmental parameters and associated with the visual display as usedon at least a second electronic device; identifying touch patterns fromthe plurality of touch event data sets; monitoring subsequent touchevents by the user of the visual display; detecting a match between thetouch patterns and the subsequent touch events of the user; predicting,in response to detecting the match, a possible touch event for the user;and modifying, in response to the possible touch event, the visualdisplay on the first electronic device for the user.
 12. The computerprogram product of claim 11, wherein the touch event data sets specifysequences of touch events, touch coordinates relative to the visualdisplay and different types of touch events.
 13. The computer programproduct of claim 11, wherein modifying the visual display includesmoving an item into a field of view of the visual display.
 14. Thecomputer program product of claim 11, wherein modifying the visualdisplay includes displaying touch event data of other users.
 15. Thecomputer program product of claim 11, wherein the touch patternscomprise at least one touch event performed on a visual display thatlacks an interactive component.